Docker rundeck image - Cannot invoke method removeMatching()

#1

As per the guide , i created oracle and ran rundeck image but i am getting issue when running docker compose up -d rundeck ldap

followed instruction created for me by megadrive :

Error :

[2021-07-26T19:35:36,408] ERROR boot.SpringApplication - Application run failed
[2021-07-26T19:35:36,869] ERROR context.BootStrapClassRunner - Error occurred running Bootstrap destroy method: Cannot invoke method removeMatching() on null object
[ec2-user@ip-10-132-150-40 efs_rundeck_dev]$ docker container logs 05c04dbb800d | grep ERROR

Question :

I am running my docker compose from mount folder and placed lib folder and jdbc jar under that . Is that correct ?

docker-compose.txt (1.6 KB) (upload://bNSye1QVEPuAkVj4GuoOf9mvmE7.txt) (45.1 KB)

56%20PM
Screen Shot 2021-07-26 at 2.58.56 PM.png1549×133 11.8 KB

#2

Hi Sankaran,

Remember that basically, you need to start the Oracle container first and configure it to create the Rundeck database, and later start the Rundeck and LDAP containers.

I added the case on my repository, a complete environment here to test, check the README instructions.

Hope it helps!

#3

I did the same way . created user in oracle container and called that user rundeck .

as mentioned in the document “https://github.com/rundeck/rundeck/issues/7180”

#4

59%20PM
Screen Shot 2021-07-26 at 3.52.59 PM.png1549×701 16.9 KB

I see tables are created by the image under the rundeckuser but page is not loading because of

[2021-07-26T19:35:36,408] ERROR boot.SpringApplication - Application run failed
[2021-07-26T19:35:36,869] ERROR context.BootStrapClassRunner - Error occurred running Bootstrap destroy method: Cannot invoke method removeMatching() on null object
[ec2-user@ip-10-132-150-40 efs_rundeck_dev]$ docker container logs 05c04dbb800d | grep ERROR

#5

Hi Sankaran,

Could you post the full error stack to take a look?

Regards.

#6

error.txt (45.1 KB)

attached log files for your reference
error_1.txt (30.1 KB)

attached two error log files for your reference . .

#7

Hi Sankaran,

Checking your log file it seems that you’re facing a 3.4.X issue related to database resources locked by Rundeck, that’s happened before in this thread (check the workaround here). You can try restarting the Oracle container or just recreating the container again.

It seems a new kind of problem, please open a new issue on GitHub.

Just in case, I tested again the docker repository environment (step by step) and it works.

Greetings!